-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup a NULL provider #2
Conversation
031fc50
to
1470a7b
Compare
Will breakdown the commits so its easier to review. |
86e7c96
to
8bb0be2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I see that we are dealing with conversions from c and rust in the provider itself. I think it would be good to have an abstraction layer on the openssl2 layer which handles the conversions, and on the provider we just deal make calls to those conversions to get safe Rust types, so that we only deal with Rust on the provider level.
- Some nits/things to check and minor changes
Yes thanks for comment. Will fix this. :) |
Should we also add the .h header files with the necessary information for calling bindgen (and include bindgen in the Cargo.toml) so that we can regenerate the bindings for any platforms? This would be consistent with our approach on the rest of the projects |
This approach would be better. Will make the changes. |
8bb0be2
to
3060f15
Compare
f047feb
to
40e59fb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some questions and changes requests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, so far so good
1f3d23a
to
9965c81
Compare
719e5ff
to
9809d8d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we avoid using the imports with "crate::*"
For example "openssl2::*".
Let's avoid collisions and be specific about what we import.
818e9ec
to
40e4b1d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏻
@@ -0,0 +1,77 @@ | |||
// Copyright 2023 Contributors to the Parsec project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this technically be 2024
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I started the PR work in 2023 December :) So kept it. Should I switch to 24?
This patch adds supports for building bindings for the missing provider related bindings and other required types. Signed-off-by: Gowtham Suresh Kumar <[email protected]>
This patch adds macros and other functions required for setting up the provider. Signed-off-by: Gowtham Suresh Kumar <[email protected]>
This patch adds the NULL provider functionality without any crypto support. The idea of this patch is to provide a working openssl provider to add features on top off. Signed-off-by: Gowtham Suresh Kumar <[email protected]>
This adds a new crate which helps in building a dynamic library for the parsec provider. Signed-off-by: Gowtham Suresh Kumar <[email protected]> shared merge
Signed-off-by: Gowtham Suresh Kumar <[email protected]>
The CI script is now updated with build steps and basic test commands to verify the dynamic loading of the parsec provider. Signed-off-by: Gowtham Suresh Kumar <[email protected]>
39380ed
40e4b1d
to
39380ed
Compare
Rebased the PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR adds NULL provider functionality as a basic setup. There are 4 crates defined in the repo:
Apart from these, there are some basic test files (ci.sh and docker image) that will be part of the CI setup testing the implementation.
Signed-off-by: Gowtham Suresh Kumar [email protected]